<!DOCTYPE html>
<html lang="zh-CN">
<head>
  <meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=2">
<meta name="theme-color" content="#222">
<meta name="generator" content="Hexo 5.0.2">
  <link rel="apple-touch-icon" sizes="180x180" href="/images/apple-touch-icon-next.png">
  <link rel="icon" type="image/png" sizes="32x32" href="/images/favicon-32x32-next.png">
  <link rel="icon" type="image/png" sizes="16x16" href="/images/favicon-16x16-next.png">
  <link rel="mask-icon" href="/images/logo.svg" color="#222">

<link rel="stylesheet" href="/css/main.css">



<link rel="stylesheet" href="//cdn.jsdelivr.net/npm/@fortawesome/fontawesome-free@5.14.0/css/all.min.css">
  <link rel="stylesheet" href="//cdn.jsdelivr.net/npm/animate.css@3.1.1/animate.min.css">

<script class="hexo-configurations">
    var NexT = window.NexT || {};
    var CONFIG = {"hostname":"wanglong_kevin.gitee.io","root":"/","scheme":"Gemini","version":"8.0.0-rc.5","exturl":false,"sidebar":{"position":"left","display":"post","padding":18,"offset":12},"copycode":false,"bookmark":{"enable":false,"color":"#222","save":"auto"},"fancybox":false,"mediumzoom":false,"lazyload":false,"pangu":false,"comments":{"style":"tabs","active":null,"storage":true,"lazyload":false,"nav":null},"motion":{"enable":true,"async":false,"transition":{"post_block":"fadeIn","post_header":"fadeInDown","post_body":"fadeInDown","coll_header":"fadeInLeft","sidebar":"fadeInUp"}},"prism":false};
  </script>

  <meta name="description" content="quilt介绍quilt 是一个很好的patch管理工具，一般的使用步骤如下：    打上现有的所有patch，打入patch的顺序由patch目录下series文件指定 1quilt push -a  新增一个patch，然后在patch目录下就会看到这个文件名的文件，内容为空      1quilt new  002-new.patch 修改源文件，编辑器可配置       1quilt ed">
<meta property="og:type" content="article">
<meta property="og:title" content="quilt patch 语法记录">
<meta property="og:url" content="https://wanglong_kevin.gitee.io/2019/01/03/patch-syntax/index.html">
<meta property="og:site_name" content="冬天里的小木屋">
<meta property="og:description" content="quilt介绍quilt 是一个很好的patch管理工具，一般的使用步骤如下：    打上现有的所有patch，打入patch的顺序由patch目录下series文件指定 1quilt push -a  新增一个patch，然后在patch目录下就会看到这个文件名的文件，内容为空      1quilt new  002-new.patch 修改源文件，编辑器可配置       1quilt ed">
<meta property="og:locale" content="zh_CN">
<meta property="article:published_time" content="2019-01-03T02:23:49.000Z">
<meta property="article:modified_time" content="2019-01-03T02:23:49.000Z">
<meta property="article:author" content="Kevin">
<meta property="article:tag" content="patch">
<meta name="twitter:card" content="summary">


<link rel="canonical" href="https://wanglong_kevin.gitee.io/2019/01/03/patch-syntax/">


<script class="page-configurations">
  // https://hexo.io/docs/variables.html
  CONFIG.page = {
    sidebar: "",
    isHome : false,
    isPost : true,
    lang   : 'zh-CN'
  };
</script>

  <title>quilt patch 语法记录 | 冬天里的小木屋</title>
  






  <noscript>
  <style>
  body { margin-top: 2rem; }

  .use-motion .menu-item,
  .use-motion .sidebar,
  .use-motion .post-block,
  .use-motion .pagination,
  .use-motion .comments,
  .use-motion .post-header,
  .use-motion .post-body,
  .use-motion .collection-header {
    visibility: visible;
  }

  .use-motion .header,
  .use-motion .site-brand-container .toggle,
  .use-motion .footer { opacity: initial; }

  .use-motion .site-title,
  .use-motion .site-subtitle,
  .use-motion .custom-logo-image {
    opacity: initial;
    top: initial;
  }

  .use-motion .logo-line {
    transform: scaleX(1);
  }

  .search-pop-overlay, .sidebar-nav { display: none; }
  .sidebar-panel { display: block; }
  </style>
</noscript>

</head>

<body itemscope itemtype="http://schema.org/WebPage" class="use-motion">
  <div class="headband"></div>

  <main class="main">
    <header class="header" itemscope itemtype="http://schema.org/WPHeader">
      <div class="header-inner"><div class="site-brand-container">
  <div class="site-nav-toggle">
    <div class="toggle" aria-label="切换导航栏">
        <span class="toggle-line"></span>
        <span class="toggle-line"></span>
        <span class="toggle-line"></span>
    </div>
  </div>

  <div class="site-meta">

    <a href="/" class="brand" rel="start">
      <i class="logo-line"></i>
      <h1 class="site-title">冬天里的小木屋</h1>
      <i class="logo-line"></i>
    </a>
      <p class="site-subtitle" itemprop="description">The Winter Room</p>
  </div>

  <div class="site-nav-right">
    <div class="toggle popup-trigger">
    </div>
  </div>
</div>



<nav class="site-nav">
  <ul class="main-menu menu">
        <li class="menu-item menu-item-home">

    <a href="/" rel="section"><i class="fa fa-home fa-fw"></i>首页</a>

  </li>
        <li class="menu-item menu-item-tags">

    <a href="/tags/" rel="section"><i class="fa fa-tags fa-fw"></i>标签</a>

  </li>
        <li class="menu-item menu-item-categories">

    <a href="/categories/" rel="section"><i class="fa fa-th fa-fw"></i>分类</a>

  </li>
        <li class="menu-item menu-item-archives">

    <a href="/archives/" rel="section"><i class="fa fa-archive fa-fw"></i>归档</a>

  </li>
  </ul>
</nav>




</div>
        
  
  <div class="toggle sidebar-toggle">
    <span class="toggle-line"></span>
    <span class="toggle-line"></span>
    <span class="toggle-line"></span>
  </div>

  <aside class="sidebar">

    <div class="sidebar-inner sidebar-nav-active sidebar-toc-active">
      <ul class="sidebar-nav">
        <li class="sidebar-nav-toc">
          文章目录
        </li>
        <li class="sidebar-nav-overview">
          站点概览
        </li>
      </ul>

      <!--noindex-->
      <section class="post-toc-wrap sidebar-panel">
          <div class="post-toc animated"><ol class="nav"><li class="nav-item nav-level-2"><a class="nav-link" href="#quilt%E4%BB%8B%E7%BB%8D"><span class="nav-number">1.</span> <span class="nav-text">quilt介绍</span></a></li><li class="nav-item nav-level-2"><a class="nav-link" href="#quilt-%E4%BD%BF%E7%94%A8%E6%8A%80%E5%B7%A7"><span class="nav-number">2.</span> <span class="nav-text">quilt 使用技巧</span></a></li><li class="nav-item nav-level-2"><a class="nav-link" href="#patch-%E6%96%87%E4%BB%B6%E6%A0%BC%E5%BC%8F"><span class="nav-number">3.</span> <span class="nav-text">patch 文件格式</span></a></li></ol></div>
      </section>
      <!--/noindex-->

      <section class="site-overview-wrap sidebar-panel">
        <div class="site-author animated" itemprop="author" itemscope itemtype="http://schema.org/Person">
    <img class="site-author-image" itemprop="image" alt="Kevin"
      src="/images/avatar.jpg">
  <p class="site-author-name" itemprop="name">Kevin</p>
  <div class="site-description" itemprop="description">NOT a coder, but an artist.</div>
</div>
<div class="site-state-wrap animated">
  <nav class="site-state">
      <div class="site-state-item site-state-posts">
          <a href="/archives/">
        
          <span class="site-state-item-count">8</span>
          <span class="site-state-item-name">日志</span>
        </a>
      </div>
      <div class="site-state-item site-state-categories">
            <a href="/categories/">
          
        <span class="site-state-item-count">3</span>
        <span class="site-state-item-name">分类</span></a>
      </div>
      <div class="site-state-item site-state-tags">
            <a href="/tags/">
          
        <span class="site-state-item-count">11</span>
        <span class="site-state-item-name">标签</span></a>
      </div>
  </nav>
</div>



      </section>
    </div>
  </aside>
  <div class="sidebar-dimmer"></div>


    </header>

    
  <div class="back-to-top">
    <i class="fa fa-arrow-up"></i>
    <span>0%</span>
  </div>

<noscript>
  <div class="noscript-warning">Theme NexT works best with JavaScript enabled</div>
</noscript>


    <div class="main-inner post posts-expand">
      

      

    
  
  
  <article itemscope itemtype="http://schema.org/Article" class="post-block" lang="zh-CN">
    <link itemprop="mainEntityOfPage" href="https://wanglong_kevin.gitee.io/2019/01/03/patch-syntax/">

    <span hidden itemprop="author" itemscope itemtype="http://schema.org/Person">
      <meta itemprop="image" content="/images/avatar.jpg">
      <meta itemprop="name" content="Kevin">
      <meta itemprop="description" content="NOT a coder, but an artist.">
    </span>

    <span hidden itemprop="publisher" itemscope itemtype="http://schema.org/Organization">
      <meta itemprop="name" content="冬天里的小木屋">
    </span>

    
    
      <header class="post-header">
        <h1 class="post-title" itemprop="name headline">
          quilt patch 语法记录
        </h1>

        <div class="post-meta">
            <span class="post-meta-item">
              <span class="post-meta-item-icon">
                <i class="far fa-calendar"></i>
              </span>
              <span class="post-meta-item-text">发表于</span>

              <time title="创建时间：2019-01-03 10:23:49" itemprop="dateCreated datePublished" datetime="2019-01-03T10:23:49+08:00">2019-01-03</time>
            </span>
            <span class="post-meta-item">
              <span class="post-meta-item-icon">
                <i class="far fa-folder"></i>
              </span>
              <span class="post-meta-item-text">分类于</span>
                <span itemprop="about" itemscope itemtype="http://schema.org/Thing">
                  <a href="/categories/%E8%AF%AD%E6%B3%95%E8%AE%B0%E5%BD%95/" itemprop="url" rel="index"><span itemprop="name">语法记录</span></a>
                </span>
            </span>

          

        </div>
      </header>

    
    
    
    <div class="post-body" itemprop="articleBody">
        <h2 id="quilt介绍"><a href="#quilt介绍" class="headerlink" title="quilt介绍"></a>quilt介绍</h2><p>quilt 是一个很好的patch管理工具，一般的使用步骤如下：  </p>
<ul>
<li><p>打上现有的所有patch，打入patch的顺序由patch目录下series文件指定</p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">quilt push -a </span><br></pre></td></tr></table></figure></li>
<li><p>新增一个patch，然后在patch目录下就会看到这个文件名的文件，内容为空     </p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">quilt new  002-new.patch</span><br></pre></td></tr></table></figure></li>
<li><p>修改源文件，编辑器可配置      </p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">quilt edit xxx.c  </span><br></pre></td></tr></table></figure>
<a id="more"></a>
</li>
<li><p>查看修改，检查是否正确    </p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">quilt diff  </span><br></pre></td></tr></table></figure>
</li>
<li><p>将修改压入patch文件</p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">quilt refresh  </span><br></pre></td></tr></table></figure>

</li>
</ul>
<h2 id="quilt-使用技巧"><a href="#quilt-使用技巧" class="headerlink" title="quilt 使用技巧"></a>quilt 使用技巧</h2><ul>
<li><p><em>只管理patch，不管理series</em><br>我们只维护patch文件，不用关心series文件，需要我们对patch文件命名有个小小的要求，打patch的顺序与文件的排序顺序
要一致，这样就可以在打patch之前生成series文件，当然这样的工作由脚本去做，可以放在Makefile中。</p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">for patch in $(ls | sort)</span><br><span class="line">do</span><br><span class="line">        echo $patch &gt;&gt; series</span><br><span class="line">done</span><br></pre></td></tr></table></figure>
</li>
<li><p><em>patch文件的生成</em><br>大多数时候,我们都是先修改文件，然后编译运行验证，验证正确后才会想到去生成patch文件，我通常的做法是先正常的修改
文件，验证完后，在原始的代码目录下来生成patch， 第一步push，第二步new，跟正常步骤一样，然后第三步时我会edit 
打开文件但不编辑，打开就退出，将所有要修改的文件都edit打开一次。然后将之前修改过后的文件拷贝到此目录下覆盖原始
文件，这个时候quilt diff 就能看到修改了，然后再去refresh。<br>有人说为啥不用git diff 之类的来生成patch文件，因为在大多数使用patch的场景下，原始代码是不在管理中的，要是在
管理器中怎么还用patch呢？比如linux内核，如果你将所有内核代码都纳入你的代码管理中，那实际你不需要用patch的，
直接修改就完事了。如果你没有管理内核代码，那你只需管理patch即可。</p>
</li>
</ul>
<h2 id="patch-文件格式"><a href="#patch-文件格式" class="headerlink" title="patch 文件格式"></a>patch 文件格式</h2><p>即便是我们验证了正确的后再生成patch文件，但是我们之后总还是会要进行进一步的修改，也许是有错误，也许
仅仅是改个对齐格式，这种情况是非常常见的。这个时候我们是不想重复上述所有步骤的，我们只想直接修改下patch文件。
这个时候我们就需要了解下patch文件的格式语法了。下面是一个patch文件例子：   </p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br><span class="line">12</span><br><span class="line">13</span><br><span class="line">14</span><br><span class="line">15</span><br><span class="line">16</span><br><span class="line">17</span><br><span class="line">18</span><br><span class="line">19</span><br><span class="line">20</span><br></pre></td><td class="code"><pre><span class="line">Index: dnsmasq-2.78&#x2F;src&#x2F;lease.c</span><br><span class="line">&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;</span><br><span class="line">--- dnsmasq-2.78.orig&#x2F;src&#x2F;lease.c</span><br><span class="line">+++ dnsmasq-2.78&#x2F;src&#x2F;lease.c</span><br><span class="line">@@ -1093,6 +1093,7 @@ int do_script_run(time_t now)</span><br><span class="line"> #ifdef HAVE_DBUS</span><br><span class="line">       emit_dbus_signal(ACTION_DEL, lease, lease-&gt;old_hostname);</span><br><span class="line"> #endif</span><br><span class="line">+      emit_ubus_signal(ACTION_DEL, lease, lease-&gt;old_hostname, (daemon-&gt;dhcp_max - leases_left));</span><br><span class="line">       old_leases &#x3D; lease-&gt;next;</span><br><span class="line">       </span><br><span class="line">       free(lease-&gt;old_hostname); </span><br><span class="line">@@ -1128,6 +1129,7 @@ int do_script_run(time_t now)</span><br><span class="line">     emit_dbus_signal((lease-&gt;flags &amp; LEASE_NEW) ? ACTION_ADD : ACTION_OLD, lease,</span><br><span class="line">              lease-&gt;fqdn ? lease-&gt;fqdn : lease-&gt;hostname);</span><br><span class="line"> #endif</span><br><span class="line">+    emit_ubus_signal((lease-&gt;flags &amp; LEASE_NEW) ? ACTION_ADD : ACTION_OLD, lease, lease-&gt;hostname, (daemon-&gt;dhcp_max- leases_left));</span><br><span class="line">     lease-&gt;flags &amp;&#x3D; ~(LEASE_NEW | LEASE_CHANGED | LEASE_AUX_CHANGED);</span><br><span class="line">     </span><br><span class="line">     &#x2F;* this is used for the &quot;add&quot; call, then junked, since they&#39;re not in the database *&#x2F;</span><br></pre></td></tr></table></figure>

<p>以上是一个完整的patch文件，这个patch文件只修改了原始的一个文件，当然也可以是多个的。  </p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br></pre></td><td class="code"><pre><span class="line">Index: dnsmasq-2.78&#x2F;src&#x2F;lease.c</span><br><span class="line">&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;&#x3D;</span><br><span class="line">--- dnsmasq-2.78.orig&#x2F;src&#x2F;lease.c</span><br><span class="line">+++ dnsmasq-2.78&#x2F;src&#x2F;lease.c</span><br></pre></td></tr></table></figure>

<p>这个就表示以下的修改的文件的路径，相对于patch目录。   </p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br><span class="line">4</span><br><span class="line">5</span><br><span class="line">6</span><br><span class="line">7</span><br><span class="line">8</span><br><span class="line">9</span><br><span class="line">10</span><br><span class="line">11</span><br></pre></td><td class="code"><pre><span class="line">@@ -1093,7 +1093,8 @@ int do_script_run(time_t now)</span><br><span class="line"> #ifdef HAVE_DBUS</span><br><span class="line">       emit_dbus_signal(ACTION_DEL, lease, lease-&gt;old_hostname);</span><br><span class="line"> #endif</span><br><span class="line">+      emit_ubus_signal(ACTION_DEL, lease, lease-&gt;old_hostname, (daemon-&gt;dhcp_max - leases_left));</span><br><span class="line">-          i &#x3D; i+1;</span><br><span class="line">+          i++;</span><br><span class="line">       old_leases &#x3D; lease-&gt;next;</span><br><span class="line">       </span><br><span class="line">       free(lease-&gt;old_hostname); </span><br><span class="line"></span><br></pre></td></tr></table></figure>

<p>以上为一个修改块，第一行为块头信息，这一块比较关键，相对于其他的没那么显而易见。@@ -1093,7 +1093,8 @@ 这个表示
以下的修改块为源文件的第1093行开始，往下一共7行，打上patch后为文件的第1093行，往下一共8行。这里的源文件指的是在
此patch之前的，patch后是指包括此patch块之前的patch，但不包括之后的patch块(稍后举例说明)。
int do_script_run(time_t now) 表示的是函数名。 再下面的+ - 分别表示增加行和删除行，其中修改行也表示先删除再增加。
上面的patch表示增加了在源文件的第1093行开始匹配</p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br><span class="line">2</span><br><span class="line">3</span><br></pre></td><td class="code"><pre><span class="line">#ifdef HAVE_DBUS</span><br><span class="line">      emit_dbus_signal(ACTION_DEL, lease, lease-&gt;old_hostname);</span><br><span class="line">#endif</span><br></pre></td></tr></table></figure>

<p>如果不匹配即报错，一般情况下在修改的地方前后各选三行来进行匹配，匹配正确后在下面增加一行</p>
<figure class="highlight plain"><table><tr><td class="gutter"><pre><span class="line">1</span><br></pre></td><td class="code"><pre><span class="line">emit_ubus_signal(ACTION_DEL, lease, lease-&gt;old_hostname, (daemon-&gt;dhcp_max - leases_left));</span><br></pre></td></tr></table></figure>

<p>并将 i= i+1修改为i++。（此处是我特意修改）。<br>上面的patch块实际是对文件来说增加了一行。如果下面还有一个patch块修改的是1093行之后，比如是第2003行的内容，
那么块头信息应该是@@-2000,6 +2001,6@@， 如果下面有一个patch块修改的是1093行之前的内容，比如第十行，那实际是不会
影响前面两个patch块的。</p>

    </div>

    
    
    

      <footer class="post-footer">
          <div class="post-tags">
              <a href="/tags/patch/" rel="tag"># patch</a>
          </div>

        

          <div class="post-nav">
            <div class="post-nav-item">
                <a href="/2018/12/31/MapT-rule/" rel="prev" title="Map-T rule">
                  <i class="fa fa-chevron-left"></i> Map-T rule
                </a>
            </div>
            <div class="post-nav-item">
                <a href="/2019/07/23/linux-nfs/" rel="next" title="linux 下共享远程文件夹">
                  linux 下共享远程文件夹 <i class="fa fa-chevron-right"></i>
                </a>
            </div>
          </div>
      </footer>
    
  </article>
  
  
  



      

<script>
  window.addEventListener('tabs:register', () => {
    let { activeClass } = CONFIG.comments;
    if (CONFIG.comments.storage) {
      activeClass = localStorage.getItem('comments_active') || activeClass;
    }
    if (activeClass) {
      const activeTab = document.querySelector(`a[href="#comment-${activeClass}"]`);
      if (activeTab) {
        activeTab.click();
      }
    }
  });
  if (CONFIG.comments.storage) {
    window.addEventListener('tabs:click', event => {
      if (!event.target.matches('.tabs-comment .tab-content .tab-pane')) return;
      const commentClass = event.target.classList[1];
      localStorage.setItem('comments_active', commentClass);
    });
  }
</script>

    </div>
  </main>

  <footer class="footer">
    <div class="footer-inner">
      

      

<div class="copyright">
  
  &copy; 
  <span itemprop="copyrightYear">2020</span>
  <span class="with-love">
    <i class="user"></i>
  </span>
  <span class="author" itemprop="copyrightHolder">Kevin</span>
</div>
  <div class="powered-by">由 <a href="https://hexo.io/" class="theme-link" rel="noopener" target="_blank">Hexo</a> & <a href="https://theme-next.js.org/" class="theme-link" rel="noopener" target="_blank">NexT.Gemini</a> 强力驱动
  </div>

      








    </div>
  </footer>

  
  <script src="//cdn.jsdelivr.net/npm/animejs@3.2.0/lib/anime.min.js"></script>
<script src="/js/utils.js"></script><script src="/js/motion.js"></script><script src="/js/next-boot.js"></script>

  















  

  

</body>
</html>
